Kramer turns the gang onto the best soup in New York City. The problem is, the chef is a bit eccentric about the restaurant and the ordering policies. For this, he's derisively nicknamed the "Soup Nazi".

The proprietor, however, is just taking a page from good data governance. In fact, we can map several data governance principles to the Soup Nazi:

✔ Data Quality: Is the data accurate and consistent, across time and domains? The soup sure is, every character in the show raves about it being the best soup in the city, and that is consistent across the episode and through many different soup varieties.

🔐 Data Access and Security: There are strict rules for ordering soup, and if they are not followed, then no soup. Just like accessing data within an organization should require the right credentials and processes.

📦 Data Stewardship: The Soup Nazi is a careful steward of the soups, ensuring the highest quality and appropriate usage, much like a data steward within an organization.

🗃 Data Structure: Knowing the schema of your data, and how various data fields and sources map to each other, is important for good governance. The Soup Nazi maintains an archive of recipes which serve as good retention for the data management. (although his security here is poor, since Elaine accesses these files...)

If you're struggling to relay data governance to any of your stakeholders, have them watch this episode of hashtag#seinfeld

Then perhaps they'll be more understanding when you have to tell them "No data for you!"